designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm

The distinction between designing the rules coordination happens within and designing the outcomes coordination produces is not an obscure philosophical point. It is independently confirmed across nine major intellectual traditions:

Political theory (Madison): The US Constitution designs the process -- separation of powers, checks and balances, federalism -- while leaving outcomes emergent from the activity that process enables. 250 years of adaptive governance from a designed framework.

Austrian economics (Hayek): General abstract rules applying equally ("laws") versus specific directives aimed at particular outcomes ("commands"). Since Hayek argued that designed rules of just conduct enable spontaneous order of greater complexity than deliberate arrangement could achieve, the distinction is not anti-design but pro-framework.

Commons governance (Ostrom): Since Ostrom proved communities self-govern shared resources when eight design principles are met without requiring state control or privatization, 800+ empirical cases confirm that successful commons share structural properties, not specific rules.

Complexity science (Juarrero, Snowden): Since enabling constraints create possibility spaces for emergence while governing constraints dictate specific outcomes, the vocabulary precisely distinguishes the two types of design.

Internet architecture (Lessig, Zittrain): Lessig's "code is law" -- architecture constrains behavior as powerfully as legal rules. Zittrain's "generativity" -- a system's capacity to produce unanticipated change through unfiltered contributions. The internet's end-to-end principle places intelligence at edges and simplicity in the core.

Open source (Torvalds, Nakamoto): Since protocol design enables emergent coordination of arbitrary complexity as Linux Bitcoin and Wikipedia demonstrate, designed protocols produce distributed coordination without central direction.

Systems thinking (Meadows, Scott, Kelly, Kauffman): Meadows identifies "rules of the system" as high-leverage structural interventions. Scott distinguishes metis (practical wisdom) from techne (abstract rules) and endorses frameworks that enable local metis. Kelly argues that without some governance from the top, bottom-up control freezes when options are many.

The convergent argument: the framework is not optional -- it is what makes emergence possible rather than chaotic. The burden of proof flips: how would collective intelligence coordinate WITHOUT an architectural framework? It would produce chaos (no constraints) or tyranny (governing constraints imposed after the fact). Since the manifesto requires deliberate design but claims emergence is how intelligence works, designed enabling constraints are the proven resolution.

Space governance is producing a live experiment in exactly this distinction. The Artemis Accords replace multilateral treaty-making with bilateral norm-setting to create governance through coalition practice rather than universal consensus -- a real-world instance of designing coordination rules (voluntary bilateral frameworks for behavior) rather than coordination outcomes (prescribing what specific activities are permitted). And the stakes are highest where the design window is still open: space settlement governance must be designed before settlements exist because retroactive governance of autonomous communities is historically impossible, meaning the rules-versus-outcomes distinction is not academic but determines whether off-world communities emerge within enabling constraints or face governing constraints imposed after the fact.

---

Relevant Notes:
- the manifesto requires deliberate design but claims emergence is how intelligence works -- this note provides the comprehensive resolution
- enabling constraints create possibility spaces for emergence while governing constraints dictate specific outcomes -- the precise vocabulary
- Ostrom proved communities self-govern shared resources when eight design principles are met without requiring state control or privatization -- the empirical evidence
- Hayek argued that designed rules of just conduct enable spontaneous order of greater complexity than deliberate arrangement could achieve -- the economic theory
- protocol design enables emergent coordination of arbitrary complexity as Linux Bitcoin and Wikipedia demonstrate -- the open source evidence
- the six axioms generate design requirements that make the infrastructure non-optional -- the manifesto's version of this argument
- the Artemis Accords replace multilateral treaty-making with bilateral norm-setting to create governance through coalition practice rather than universal consensus -- real-world example of designing coordination rules not outcomes in the space domain
- space settlement governance must be designed before settlements exist because retroactive governance of autonomous communities is historically impossible -- the design window for space settlement rules illustrates why the rules-versus-outcomes distinction has existential stakes
- strategy is a design problem not a decision problem because value comes from constructing a coherent configuration where parts interact and reinforce each other -- Rumelt adds strategic management to the traditions distinguishing rule-design from outcome-specification
- mechanism design changes the game itself to produce better equilibria rather than expecting players to find optimal strategies -- ATLB formalizes the rule-vs-outcome distinction as mechanism design: changing the game's rules so greedy agents converge on better equilibria without needing to compute global optima

Topics:
- maps/livingip overview
- emergence and complexity
- maps/coordination mechanisms